Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
| npm run spicedb:sample | ||
| ``` | ||
|
|
||
|  |
There was a problem hiding this comment.
created: user:alice is owner of farm:1
then what is the point of writing that user:alice is an admin of the organization that owns farm:1?
There was a problem hiding this comment.
i didn't get it 🤔
There was a problem hiding this comment.
in the image you are showing 3 tuple writes:
org:1 # admin @ user:alicefarm:1 # owner @ org:1farm:1 # owner @ user:alice
then you are checking: farm:1 # view @ user:alice ?
the schema says permission view = viewer + editor + owner + organization->view
so, you can answer "yes" with tuples (1) and (2), or with tuple (3).
my point was - why bother writing (1) and (2) when (3) already answers "yes"?
There was a problem hiding this comment.
In this case the third tuple write is not necessary, but i'm assuming the original author (rohit from motia + some LLM) added it in in case there was a change later for a distinct authz part.
Let's leave it as is for now, imo
Co-authored-by: Maria Ines Parnisari <maria.ines.parnisari@authzed.com>
Co-authored-by: Maria Ines Parnisari <maria.ines.parnisari@authzed.com>
Co-authored-by: Maria Ines Parnisari <maria.ines.parnisari@authzed.com>
|
Deployment failed with the following error: View Documentation: https://vercel.com/docs/accounts/team-members-and-roles |
|
Preview deployment status for this pull request.
|
2 participants
Added the Motia guide from the blog (https://authzed.com/blog/building-a-multi-tenant-rag-with-fine-grain-authorization-using-motia-and-spicedb) also to the tutorials section of docs